-
Notifications
You must be signed in to change notification settings - Fork 1.4k
✨ Add EncryptionAlgorithm to Kubeadmconfig #12859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Need to add Unit test cases and fix existing tests Not super confident about the changes, Have broken some interfaces as well, Based on the initial review and if the path chosen is correct, I will update accordingly. @sbueringer Please take a look when time permits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx! I think I covered the open points, but just ping me if you want to discuss anything else.
Definitely feel free to ping me again after the next iteration on the prod code for another quick review
|
|
||
| // Generate Cluster Kubeconfig if needed | ||
| if result, err := r.reconcileKubeconfig(ctx, controlPlane); !result.IsZero() || err != nil { | ||
| if result, err := r.reconcileKubeconfig(ctx, controlPlane); err != nil || !result.IsZero() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert this one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverted it.
May not be either needed or relevant wrt to this PR, but I feel its better to maintain a standard for this, I see some places
!result.IsZero() || err != nil and in some other err != nil || !result.IsZero()
IDE suggesting to check error first
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. Makes sense and I agree with checking error first. Let's just do this everywhere and in a separate PR.
Feel free to open a PR, but please on top of #12857 / or after 12857 is merged (I get rid of some of these cases in that PR)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I will do it later. Thank you.
|
@sbueringer thanks for the review, I have updated accordingly and ready for next round of review. Please take a look when time permints. I tried in the approach of changing the existing thing rather than avoiding the breakage for users, I will remember it for the next time. Thanks |
All good. I think it's a bit of a trade-off and probably also a case-by-case decision. Thx for asking for early feedback! I'll take another look |
|
Did another quick round of review. I think the e2e test failure might just be a flake but let's see /retest If tests are green and the findings above are addressed I would do a full review (just need a bigger block of time for that) |
| g.Expect(err).ToNot(HaveOccurred()) | ||
|
|
||
| workloadCluster, err := m.GetWorkloadCluster(ctx, tt.clusterKey) | ||
| workloadCluster, err := m.GetWorkloadCluster(ctx, tt.clusterKey, "") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use the default encryption algo instead of ""
|
Some misconfiguration, will check |
|
Maybe similar to #12859 (comment) |
|
Just checking again to make sure it passes. |
|
/test pull-cluster-api-e2e-main Triggering all for more data |
|
I'll try to review again ASAP. Hopefully tomorrow or so |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Karthik-K-N Thank you very much!
Last round of minor findings from my side
I also already did some testing with Tilt and everything looks good
|
Addressed all the review comments. Please take a look when time permits, Thanks. |
util/conditions/:root:kubernetes:_output:local:go:bin:ginkgo -time
Outdated
Show resolved
Hide resolved
|
@Karthik-K-N Thx! Very last nit from my side. /assign @fabriziopandini |
|
/test pull-cluster-api-e2e-main (please trigger ^^ again after you fixed the last finding) |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test pull-cluster-api-e2e-main |
I will submit a follow up soon, Thank you. |
|
@Karthik-K-N: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Thx! /lgtm |
|
LGTM label has been added. Git tree hash: 416ca4fa275bafe77248da3bcec1e942993edd94
|
What this PR does / why we need it:
This PR adds EncryptionAlgorithm to KubeadmConfig and necessary changes
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes ##10077
/area provider/bootstrap-kubeadm